Graceful designated router handoff

ABSTRACT

In one embodiment, a first Protocol Independent Multicast (PIM) router includes port interfaces to receive multicast traffic from a first network and forward the traffic to at least one receiver, which is in a sub-network including other PIM routers, and a routing processor configured, in response to a decision for the first PIM router to relinquish being a designated router, to generate a PIM Hello message with a first option descriptor and a first priority, the first option descriptor indicating a staggered handoff process, and send the PIM Hello message, receipt of the PIM Hello message by the other PIM routers being operative to result in a designated router election electing a new designated router, the new designated router being operative to initiate the staggered handoff process causing the first PIM router to continue forwarding traffic until the new designated router has built a multicast routing tree.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/839,886, filed Dec. 13, 2017, the entire contents of which areincorporated herein by reference.

TECHNICAL FIELD

The present disclosure generally relates to handoff of designated routerrole to another router.

BACKGROUND

Protocol Independent Multicast (PIM) is a widely deployed multicastprotocol. As defined in Request for Comments (RFC) 7761 of the InternetEngineering Task Force (IETF), a PIM designated router (DR) election isperformed in each shared local area network (LAN). A PIM DR isresponsible for creating a multicast routing tree upstream. There aremany network events, which could initiate a PIM DR re-election. Networkevents that would trigger DR re-election may be classified intonon-deterministic events and deterministic network events. Non-limitingexamples of non-deterministic network events include a router,designated as PIM DR, restarting due to power failure or any otherhardware failure, which cannot be predicted in advance, or an interfacefailure. Non-limiting examples of deterministic network events include arouter, designated as a PIM DR, going in to maintenance mode, a newrouter coming up in a network, or a configuration change (e.g., changein priority of the current PIM DR or another one of the PIM routers inthe LAN).

Currently, when a PIM router relinquishes its PIM DR role, the PIMrouter generally: lowers its priority (statically or dynamically), orsends a

PIM Hello message with zero hold-time leading to a DR re-election takingplace; and stops forwarding traffic. Meanwhile, the newly elected PIM DRstarts building a multicast routing tree which takes time, so thattraffic is lost while the multicast routing tree is being built.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood and appreciated more fullyfrom the following detailed description, taken in conjunction with thedrawings in which:

FIG. 1 is a block diagram view of a designated router graceful handoffsystem constructed and operative in accordance with an embodiment of thepresent disclosure;

FIG. 2 is a flow chart including exemplary steps in a method ofoperation of a router in the system of FIG. 1; and

FIG. 3 is a flow chart including exemplary steps in a method ofoperation of another router in the system of FIG. 1.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

There is provided in accordance with an embodiment of the presentdisclosure, a first Protocol Independent Multicast (PIM) routerincluding a plurality of port interfaces configured to receive multicasttraffic from a first network and forward the multicast traffic to atleast one receiver, which is in a sub-network, the sub-network includinga plurality of other PIM routers, and a routing processor configured, inresponse to a decision for the first PIM router to relinquish being adesignated router in the sub-network, to generate a first PIM Hellomessage with a first option descriptor and a first priority, wherein (a)the first option descriptor indicates a staggered handoff process, and(b) the first priority is set to be lower than a priority of at leastone PIM router of the plurality of other PIM routers in the sub-network,and send the first PIM Hello message for receipt by the plurality ofother PIM routers causing a designated router election which elects anew designated router from among the plurality of other PIM routers, thenew designated router being operative to initiate the staggered handoffprocess in response to the first option descriptor, the staggeredhandoff process causing the first PIM router to continue forwardingmulticast traffic from the first network to the at least one receiveruntil the new designated router has built a multicast routing tree toreceive the multicast traffic from the first network.

DETAILED DESCRIPTION

Reference is now made to FIG. 1, which is a block diagram view of adesignated router (DR) graceful handoff system 10 constructed andoperative in accordance with an embodiment of the present disclosure.The DR graceful handoff system 10 is operative to handoff the DR role toa new DR based on a deterministic network event (e.g., shutting down aProtocol Independent Multicast (PIM) router for maintenance). Thehandoff process is performed in stages to reduce or prevent traffic lossduring handoff and is therefore referred to as a staggered handoffprocess herein below.

In overview, the staggered handoff process is initiated in a PIM router,which is relinquishing its DR role to another PIM router based on adeterministic network event. The PIM router sends a PIM Hello messagewith a new option (which may be referred to as DR graceful handoff or DRstaggered handoff) to inform a newly elected DR that staggered handoffprocessing is being requested. Therefore, both the relinquishing DR andthe newly elected DR perform the staggered handoff processing in orderto reduce or prevent traffic loss. Among other features of the staggeredhandoff process, the relinquishing DR continues to forward multicasttraffic (even after the PIM Hello message with the new option has beensent) until the newly elected DR has successfully built the multicastrouting tree and forwards the multicast traffic. It should be noted thatthe DR graceful handoff system 10 generally provides staggered handofffor a last hop router.

A PIM Hello message is a PIM message with the type field equal to zero.A PIM Hello message includes option type, option length, and optionvalue fields. One or more of the option fields may be used to identify aPIM Hello message as a PIM Hello message to initiate a DR staggeredhandoff. The term option descriptor used in the specification and claimsmay refer to one or more of the option fields mentioned above.

The DR graceful handoff system 10 is now described in more detail withreference to the various elements of FIG. 1. FIG. 1 shows three PIMrouters, router R1, router R2 and router R3. Initially, the PIM routerR1 is elected as the DR. The PIM router R1 receives multicast trafficfrom one or more networks 12 (e.g. one or more core networks) andforwards the multicast traffic to one or more receivers 14. The PIMrouters R1, R2, and R3 are disposed in a subnetwork 16, e.g., a last hopshared local area network (LAN).

In response to a decision (typically, but not necessarily, by the PIMrouter R1) to relinquish being a DR in the subnetwork 16, the PIM routerR1 is configured to generate a PIM Hello message with an optiondescriptor and a priority and send the PIM Hello message for receipt bythe other PIM routers in the subnetwork 16. The option descriptorindicates that the PIM Hello message is a PIM Hello message to initiatea DR staggered handoff. The priority is set to be lower than a priorityof at least one of the other PIM routers in the subnetwork 16. Thepriority in the PIM Hello message is set to be lower than a priority ofat least one other PIM router in the subnetwork 16 so that the PIMrouter R1 does not win a DR election triggered by sending the PIM Hellomessage. In order to simplify priority setting, the priority of the PIMHello message may be set to equal zero by the PIM router R1.

Receipt of the PIM Hello message by the other PIM routers in thesubnetwork 16 (e.g., R2 and R3) triggers a DR election mechanism in thesubnetwork 16. For the sake of illustration, it is assumed that the PIMrouter R3 wins the DR election and is now the new DR in the subnetwork16.

At this stage, the PIM router R3 commences to build a multicast routingtree upstream towards the network(s) 12 for each multicast group of aplurality of multicast groups having local receivers, and to generate anegress interface connected to subnetwork 16, for each of the multicastgroups having local receivers. The PIM router R3 also starts a failsafetimer, which is described in more detail below. At this stage, the PIMrouter R1 continues forwarding received multicast traffic towards thereceiver(s) 14. The term “group” used herein refers to multicast group.It should also be noted that any reference to “group” herein, mightrefer to a source/multicast-group pair.

By way of introduction, in according with PIM, a PIM router may generatea data driven assert when receiving duplicate traffic. In the currentsituation, if the PIM router R3 generates a data driven assert, at thisstage before the multicast routing tree is built, the PIM router R1 mayissue a PIM Assert Cancel message and would stop forwarding multicasttraffic resulting in traffic loss. For example, the PIM router R3 mayreceive traffic via the egress interface, which without receipt of thePIM Hello message would result in the PIM router R3 generating a datadriven assert and traffic loss. However, in accordance with thestaggered handoff process, the PIM router R3 is configured to refrainfrom generating a data driven assert after the PIM Hello message isreceived until, the earlier of: the PIM router R3 receiving a PIM AssertCancel message (or similar message) from the PIM router R1; or thefailsafe timer reaching the end of a timeout period. The failsafe timeris started so that the PIM router R3 reverts to allowing the generationof a data driven Assert even if the PIM router R1 fails to send the PIMAssert Cancel message due to an unavoidable network event or if the PIMAssert Cancel message is not received by R3. It should be noted that thePIM message and the DR role are group and flow independent, whereas themulticast routing tree, the egress interface, and the Assert messagesare group or flow specific.

As soon as the PIM router R3 starts receiving multicast traffic from thenetwork(s) 12, the PIM router R3 forwards the multicast traffic to thereceiver(s) 14. Since the PIM router R1 has sent the PIM Hello message,the PIM router R1 sends a PIM Assert Cancel, for receipt by the PIMrouter R3, when the PIM router R1 receives duplicate multicast trafficfor a flow. At this stage, the PIM router R1 stops forwarding themulticast traffic for the group associated with the flow having theduplicate multicast traffic. When the PIM router R3 receives the PIMAssert Cancel, it reverts to allowing generation of a data driven Assertfor that group. When detecting duplicate traffic for a group, the PIMrouter R1 sends a PIM Assert Cancel for that group for receipt by thePIM router R3 and stops forwarding traffic for that group. The above isperformed for other groups until the PIM router R1 is no longerforwarding traffic.

At this stage, the PIM router R3 is now forwarding all the multicasttraffic received from the network(s) 12 to the receiver(s) 14, and thePIM router R1 is not forwarding multicast traffic from the network(s) 12to the receiver(s) 14. The PIM router R1 may now transition tomaintenance mode if that was the deterministic network event thattriggered the PIM router R1 to send the PIM Hello message.

It will be appreciated that the PIM router R1 may also have beentriggered to send the PIM Hello message with the staggered handoffprocessing option if another PIM router with a higher priority joins thesubnetwork 16 or if a current PIM router in the subnetwork 16 now has ahigher priority than the PIM router R1.

Assuming that the PIM router R1 transitioned to maintenance mode and nowthe PIM router R1 transitions from maintenance mode back to operationalmode, the PIM router R1 send a PIM Hello message with the real priorityof the PIM router R1. The PIM router R3 detects that the PIM router R1has a higher priority than the PIM router R3 which triggers the PIMrouter R3 to send a PIM Hello message with the staggered handoffprocessing option in order to initiate a staggered transfer from the PIMrouter R3 back to the PIM router R1 based on the staggered handoffprocessing described above. In this case, the PIM Hello message prioritycan be the real priority of the PIM router R3 because the PIM router R1has a higher priority than the priority of the PIM router R3.

As described above, the DR graceful handoff system 10 allows a smoothtransition of a last hop DR. The DR graceful handoff system 10 does notneed to handle smooth transition of a first hop DR to another first hopDR.

The DR graceful handoff system 10 may be implemented in a sub-networkwhere all the PIM routers are configured to recognize the PIM Hellomessage with the staggered handoff process option and process thestaggered handoff process. Additionally, the DR graceful handoff system10 may be implemented in a hybrid network where one or more routers(compliant routers) are configured to recognize the PIM Hello messagewith the staggered handoff process option and process the staggeredhandoff process, and one or more routers (non-compliant routers) do notrecognize the PIM Hello message with the staggered handoff processoption and do not process the staggered handoff process. By way ofexample, consider a hybrid network including six PIM routers, R1, R2,R3, R4, R5, and R6 in the subnetwork 16 (note that PIM routers R4, R5,and R6 are not shown in FIG. 1). Routers R1 to R4 are compliant routersand routers R5 and R6 are non-compliant routers. Assuming that R1 isinitially the DR and a decision is made for R1 to relinquish the DRrole. R1 sends out a PIM Hello message with the staggered handoffprocess option. If the newly elected DR is one of the compliant routers,the process described above for staggered handoff in R1 and in the newlyelected DR is performed. If the newly elected DR is one of thenon-compliant routers, then the newly elected DR would start to build amulticast routing tree upstream and when traffic is detected by thenewly elected DR, the newly elected DR would generate a data drivenAssert. If R1 sends any Assert messages, as specified in the PIMprotocol, while R1 is a relinquishing DR, R1 may optionally set theAssert message metric to infinity. Setting the Assert metric to infinityensures that R1 loses the Assert state to the newly elected DR, whichwill start to receive and forward multicast traffic as the multicastrouting tree is built.

The PIM router R1 of FIG. 1 includes a plurality of port interfaces 18-1and a routing processor 20-1 and other elements (not shown). The portinterfaces 18-1 are configured to receive multicast traffic from thenetwork(s) 12 and forward the multicast traffic to the at least onereceiver 14. The routing processor 20-1 is described in more detailbelow with reference to FIG. 2.

The PIM router R3 of FIG. 1 includes a plurality of port interfaces 18-3and a routing processor 20-3 and other elements (not shown). Theplurality of port interfaces 18-3 are configured to receive and forwardmulticast traffic. The routing processor 20-3 is described in moredetail below with reference to FIG. 3.

The DR graceful handoff system 10 is now described in more detail withreference to FIGS. 2 and 3 based on the assumption that the initial PIMDR is the PIM router R1 and the newly elected DR is the PIM router R3.

Reference is now made to FIG. 2, which is a flow chart 22 includingexemplary steps in a method of operation of the router R1 in the system10 of FIG. 1. Reference is also made to FIG. 1.

The routing processor 20-1 is configured, in response to a decision forthe PIM router R1 to relinquish being a DR in the sub-network 16, togenerate a first PIM Hello message with a first option descriptor and afirst priority (block 24). The first option descriptor indicates astaggered handoff process. The first priority is set to be lower than apriority of at least one PIM router of the other

PIM routers in the sub-network 16. The first priority may be set toequal zero.

The routing processor 20-1 is configured, in response to the decisionfor the PIM router R1 to relinquish being a DR in the sub-network 16, tosend the first PIM Hello message for receipt by the other PIM routers inthe sub-network 16 (block 26). Receipt of the first PIM Hello message bythe other PIM routers in the subnetwork 16 is operative to result in aDR election, which elects a new DR (the PIM router R3) from among theother PIM routers. The new DR (the PIM router R3) is operative toinitiate the staggered handoff process in response to the first optiondescriptor. The staggered handoff process causes the PIM router R1 tocontinue forwarding multicast traffic from the network(s) 12 to the atleast one receiver 14 until the new DR (the PIM router R3) has built amulticast routing tree to receive the multicast traffic from thenetwork(s) 12.

The routing processor 20-1 is configured, in response to receivingduplicate multicast traffic for a first group from the network(s) 12 onat least one of the plurality of interface ports 18-1, to: generate asecond PIM message (e.g., a PIM Assert Cancel message or a custom PIMmessage) for the first group (block 28); send the second PIM message tothe new DR (the PIM router R3) (block 30); and stop forwarding multicastnetwork traffic for the first group from the network(s) 12 to the atleast one receiver 14 (block 32). The second PIM message indicates thatthe new DR (the PIM router R3) is permitted to generate a data drivenPIM assert with respect to the first group. At decision block 34, therouting processor 20-1 determines if there is still traffic of othergroups being forwarded. If there are more groups for which traffic isbeing forwarded by the PIM router R1 (branch 36), the steps of blocks28-32 are repeated for the other groups when duplicate traffic for theother groups is received. If there are no more groups for which trafficis being forwarded by the PIM router R1 (branch 38), the routingprocessor 20-1 is configured to move the PIM router R1 into amaintenance mode (block 40). It should be noted that the step of block40, and the steps of blocks 42 and 44 described below, are performed ifthe deterministic network event, which triggered the PIM router R1 tosend the first Hello message, was to transition the PIM router R1 intomaintenance mode.

The routing processor 20-1 is configured: in response to returning fromthe maintenance mode, to generate and send a third PIM Hello messagewith a second priority which is higher than the priority of the new DR(the PIM router R3) (block 42); and receive a fourth PIM Hello messagefrom the new DR (the PIM router R3) with an option descriptor indicatinga staggered handoff process from the new DR (the PIM router R3) (block44).

Reference has been made herein to first, second, third, and fourthmessages in the specification and claims. It should be noted that theterm “first”, “second” etc. does not refer to an order of the messages,but is used as a way to differentiate one message from another. Itshould also be noted that each of the messages (first, second, third,and fourth) might be sent repeatedly and periodically. For example, thefirst PIM Hello message may be sent periodically by R1 until R1transitions into maintenance mode, and while in maintenance mode R1 maysend period PIM Hello messages with a low priority (without the optiondescriptor indicating a staggered handoff process). Additionally, thesecond PIM message may be group specific giving a second PIM message pergroup (source-group pair).

Reference is now made to FIG. 3, which is a flow chart 46 includingexemplary steps in a method of operation of the PIM router R3 in thesystem 10 of FIG. 1. Reference is also made to FIG. 1. The routingprocessor 20-3 is configured to receive, from the PIM router R1 (whichis a DR in a sub-network 16), the first PIM Hello message with the firstoption descriptor and the first priority (block 48).

The routing processor 20-3 is configured, in response to receiving thefirst PIM Hello message, to participate in the DR election (block 50),which elects the PIM router R3 as the new DR from among the plurality ofother PIM routers. The routing processor 20-3 is configured to initiatethe staggered handoff process in response to the first option descriptor(block 52).

In accordance with the staggered handoff process of block 52, therouting processor 20-3 is configured to perform the steps of blocks54-62 described in more detail below. The routing processor 20-3 isconfigured to start a timer to track the end of the timeout period(block 54). The timer may be started from receiving the first PIM Hellomessage or from being elected as the DR or any other suitable starttime. The routing processor 20-3 is configured to build the multicastrouting tree, for each multicast group of a plurality of multicastgroups having local receivers, to receive the multicast traffic from thenetwork(s) 12 (block 56). The routing processor 20-3 is configured togenerate the egress interface, for each of the multicast groups havinglocal receivers, to forward multicast traffic towards the at least onereceiver 14 (block 58).

The routing processor 20-3 is configured to refrain from generating adata driven Assert (block 60) until the earlier of: (a) receipt of thesecond PIM message (e.g., a PIM Assert Cancel message or other custommessage) from the PIM router R1; or (b) reaching the end of the timeoutperiod. The second PIM message may be group specific as explained above.The routing processor 20-3 is configured to revert to allowinggeneration of a data driven Assert (for the group for which the secondPIM message was received) (block 62) after the earlier of: (a) receiptof the second PIM message (for that group) from the PIM router R1; or(b) reaching the end of the timeout period. As the second PIM message isgroup specific, refraining from generating a data driven Assert for agroup will be maintained until the second PIM message for that group isreceived from the PIM router R1 or until reaching the end of the timeoutperiod (whichever is earlier). At this point, the port interfaces 18-3are configured to receive the multicast traffic from the network(s) 12and forward the multicast traffic to the at least one receiver 14 in thesub-network 16.

Based on an event, for example, but not limited to, the PIM router R1transitioning from maintenance mode to operational mode, the routingprocessor 20-3 is configured to receive, from the PIM router R1, thethird PIM Hello message with the second priority, which is higher thanthe priority of the PIM router R3 (block 64). The routing processor 20-3is configured, in response to receiving the third PIM Hello message withthe second priority, which is higher than the priority of the PIM routerR3, to generate and send a fourth PIM Hello message with an optiondescriptor indicating a staggered handoff process from the PIM router R3(block 66).

In practice, some or all of the functions of each routing processor 20may be combined in a single physical component or, alternatively,implemented using multiple physical components. These physicalcomponents may comprise hard-wired or programmable devices, or acombination of the two. In some embodiments, at least some of thefunctions of the processing circuitry may be carried out by aprogrammable processor under the control of suitable software. Thissoftware may be downloaded to a device in electronic form, over anetwork, for example. Alternatively or additionally, the software may bestored in tangible, non-transitory computer-readable storage media, suchas optical, magnetic, or electronic memory.

It is appreciated that software components may, if desired, beimplemented in ROM (read only memory) form. The software components may,generally, be implemented in hardware, if desired, using conventionaltechniques. It is further appreciated that the software components maybe instantiated, for example: as a computer program product or on atangible medium. In some cases, it may be possible to instantiate thesoftware components as a signal interpretable by an appropriatecomputer, although such an instantiation may be excluded in certainembodiments of the present disclosure.

It will be appreciated that various features of the disclosure whichare, for clarity, described in the contexts of separate embodiments mayalso be provided in combination in a single embodiment. Conversely,various features of the disclosure which are, for brevity, described inthe context of a single embodiment may also be provided separately or inany suitable sub-combination.

It will be appreciated by persons skilled in the art that the presentdisclosure is not limited by what has been particularly shown anddescribed hereinabove. Rather the scope of the disclosure is defined bythe appended claims and equivalents thereof.

What is claimed is:
 1. A method comprising: receiving, by a first routerfrom a second router, a first Hello message with a first optiondescriptor and a first priority, wherein the second router is adesignated router in a sub-network; in response to receiving the firstHello message, participating in a designated router election whichelects the first router as a new designated router from among aplurality of other routers in the sub-network; and initiating astaggered handoff process in response to the first option descriptor,the staggered handoff process causing the second router to continueforwarding multicast traffic from a first network to at least onereceiver until the new designated router has built a multicast routingtree to receive the multicast traffic from the first network.
 2. Themethod of claim 1, wherein the first option descriptor indicates thestaggered handoff process and the first priority is set to be lower thana priority of at least one router of the plurality of other routers inthe sub-network.
 3. The method of claim 1, wherein the first priority isset equal to zero.
 4. The method of claim 1, wherein the first router isa first Protocol Independent Multicast (PIM) router and the secondrouter is a second PIM router.
 5. The method of claim 1, wherein thestaggered handoff process comprises: building, by the first router,which is the new designated router, the multicast routing tree toreceive the multicast traffic from the first network; generating anegress interface to forward multicast traffic towards the at least onereceiver; refraining from generating a data driven Assert until: (a)receipt of a second message from the second router, the second messageindicating that the new designated router is permitted to generate adata driven Assert; or (b) reaching an end of a timeout period; andreceiving the multicast traffic from the first network and forwardingthe multicast traffic to the at least one receiver in the sub-network.6. The method of claim 5, wherein the staggered handoff process furthercomprises reverting to allow generation of a data driven Assert after:(a) receipt of the second message from the second router; or (b)reaching the end of the timeout period.
 7. The method of claim 5,further comprising: starting a timer to track the end of the timeoutperiod.
 8. The method of claim 5, wherein the second message is aProtocol Independent Multicast (PIM) Assert Cancel message.
 9. One ormore non-transitory computer readable storage media encoded withinstructions that, when executed by a processor, cause the processor toperform operations, comprising: receiving, by a first router from asecond router, a first Hello message with a first option descriptor anda first priority, wherein the second router is a designated router in asub-network; in response to receiving the first Hello message,participating in a designated router election which elects the firstrouter as a new designated router from among a plurality of otherrouters in the sub-network; and initiating a staggered handoff processin response to the first option descriptor, the staggered handoffprocess causing the second router to continue forwarding multicasttraffic from a first network to at least one receiver until the newdesignated router has built a multicast routing tree to receive themulticast traffic from the first network.
 10. The media claim 9, whereinthe first option descriptor indicates the staggered handoff process andthe first priority is set to be lower than a priority of at least onerouter of the plurality of other routers in the sub-network.
 11. Themedia of claim 9, wherein the first priority is set equal to zero. 12.The media of claim 9, wherein the staggered handoff process comprises:building, by the first router, which is the new designated router, themulticast routing tree to receive the multicast traffic from the firstnetwork; generating an egress interface to forward multicast traffictowards the at least one receiver; refraining from generating a datadriven Assert until: (a) receipt of a second message from the secondrouter, the second message indicating that the new designated router ispermitted to generate a data driven Assert; or (b) reaching an end of atimeout period; and receiving the multicast traffic from the firstnetwork and forwarding the multicast traffic to the at least onereceiver in the sub-network.
 13. The media of claim 12, wherein thestaggered handoff process further comprises reverting to allowgeneration of a data driven Assert after: (a) receipt of the secondmessage from the second router; or (b) reaching the end of the timeoutperiod.
 14. The media of claim 12, wherein the staggered handoff processfurther comprises starting a timer to track the end of the timeoutperiod.
 15. The media of claim 12, wherein the second message is aProtocol Independent Multicast (PIM) Assert Cancel message.
 16. A firstrouter comprising: a processor configured to: receive, from a secondrouter, a first Hello message with a first option descriptor and a firstpriority, wherein the second router is a designated router in asub-network; in response to receiving the first Hello message,participate in a designated router election which elects the firstrouter as a new designated router from among a plurality of otherrouters in the sub-network; and initiate a staggered handoff process inresponse to the first option descriptor, the staggered handoff processcausing the second router to continue to forward multicast traffic froma first network to at least one receiver until the new designated routerhas built a multicast routing tree to receive the multicast traffic fromthe first network.
 17. The first router of claim 16, wherein the firstoption descriptor indicates the staggered handoff process and the firstpriority is set to be lower than a priority of at least one router ofthe plurality of other routers in the sub-network.
 18. The first routerof claim 16, wherein the first priority is set equal to zero.
 19. Thefirst router of claim 16, wherein for the staggered handoff process theprocessor is configured to: build the multicast routing tree to receivethe multicast traffic from the first network; generate an egressinterface to forward multicast traffic towards the at least onereceiver; and refrain from generating a data driven Assert until: (a)receipt of a second message from the second router, the second messageindicating that the new designated router is permitted to generate adata driven Assert; or (b) reaching an end of a timeout period, whereina plurality of port interfaces of the first router are configured toreceive the multicast traffic from the first network and forward themulticast traffic to the at least one receiver in the sub-network. 20.The first router of claim 16, wherein the first router is a firstProtocol Independent Multicast (PIM) router and the second router is asecond PIM router.